![]() 10/03/2018 at 10:00 • Filed to: None | ![]() | ![]() |
An Antonov ran into the back of the other on the runway at a fairly high rate of speed. No details yet on how it happened or the extent of injuries.
!!! UNKNOWN CONTENT TYPE !!!
![]() 10/03/2018 at 10:04 |
|
whoops!
![]() 10/03/2018 at 10:04 |
|
Looks like one was attempting to take off snd one was landing in the same space
![]() 10/03/2018 at 10:06 |
|
It looks like the one was landing while the other was taking off, or they got cleared to land on the same runway. Either way, that’s not supposed to happen.
![]() 10/03/2018 at 10:09 |
|
When we were landing in Munich we did a touch and go because there was a plane landing next to us. Scared the living shit out of me, especially because we hit turbulence at the end of the runway.
10/03/2018 at 10:09 |
|
![]() 10/03/2018 at 10:10 |
|
huh... well.. that should be the last plane crash for a while.. i think we at 3 in about as many days now , we had the f35 and micronesia had a plane that went diving
everyone survived
and now this on the runway
incidentally over the next 4 weeks ill be taking 4 flights... hooray:)
(edit) ah... apparently one died in the micronesia crash.. but my local news never updated the story
![]() 10/03/2018 at 10:12 |
|
That’s not supposed to happen.
![]() 10/03/2018 at 10:12 |
|
That very rarely goes well.
![]() 10/03/2018 at 10:12 |
|
Yeah, I think ATC is in deep doodoo for this, then again the weather was clear and pilots have eyes....
![]() 10/03/2018 at 10:14 |
|
Could have been parallel runways and the pilots lined up on the wrong one. Hell, Air Canada tried to land on a taxiway full of planes.
![]() 10/03/2018 at 10:16 |
|
Check that, Khartoum only has a single runway.
![]() 10/03/2018 at 10:17 |
|
You’re telling me.
![]() 10/03/2018 at 10:17 |
|
South Sudan Airlines probably cut off Air Sudan on the taxiway and then it just devolved into a road rage incident.
![]() 10/03/2018 at 10:17 |
|
incidentally over the next 4 weeks ill be taking 4 flights... hooray:)
And you are still far more likely to die in a car crash than a plane crash. Depending on where you are flying, that is.
![]() 10/03/2018 at 10:19 |
|
![]() 10/03/2018 at 10:21 |
|
yeah i know.... but in a car im in control wich always makes me feel better
but my flights should be plenty safe netherlands-england, england-portugal and back with british airways i think
no worries there.... the free meal they still offer in flight is more likely to kill me than anything else :p
![]() 10/03/2018 at 10:26 |
|
The past week also produced an off runway excursion in Latvia
A gear up landing in Bangladesh
A Kalitta charter crash in Michigan
And a runway overrun in Georgia (the state not the country)
And that’s not including the small aircraft accidents.
Also one passenger from the water landing did actually die. They got out of the plane safely but apparently fell out of the rescue raft on the way to show and drowned.
![]() 10/03/2018 at 10:27 |
|
yikes bad week for aviation
and yeah i just learnt the water landing had a casualty.. my local news never updated the story
![]() 10/03/2018 at 10:31 |
|
That runway overrun was in Greenville South Carolina, about 0.5 miles from the brewery my friends and I visit every Thursday .
![]() 10/03/2018 at 10:35 |
|
The parallel runways at Munich are not that close so not sure what happened on your flight. So you actually touched the ground? Were you ahead or behind the other plane?
It gets sketchy when the parallel runways are very close together like at SFO. Planes can land next to each other, but they have to maintain the correct amount of separation. If one gets too far ahead one will have to go around to avoid wake turbulence problems.
The 747 was moving too quickly so the 757 had to go around to avoid ending up behind the 747:
![]() 10/03/2018 at 10:36 |
|
yeah i know.... but in a car im in control wich always makes me feel better
That’s true, but in the air, all the other planes are flown by professional pilots. On the road, all the other cars are driven by idiots.
![]() 10/03/2018 at 10:37 |
|
I seem to recall earlier in the year that nice Mr Trump took personal credit for the lack of any fatalities in air transport in 2017.
The record so far this year is sadly not very good but I
don’t recall the said gentleman accepting any blame.
![]() 10/03/2018 at 10:39 |
|
That’s a really interesting video. I’ve never heard of that situation, but of course, it makes complete sense. Love the sound of those engines spooling up.
![]() 10/03/2018 at 10:41 |
|
this true... its not a rational thing im just not very good at flying
not quite scared of it but not a big fan either (course im not very good at trains or buses either so i think my main issue is being in a tube full of people)
i’d go everywhere i cant drive to by boat if i had the choice and time
![]() 10/03/2018 at 10:46 |
|
Actually touched down, then the pilot immediately went to full power and took off again for a go around . M y friend said he saw a plane next to us on approach, so maybe it ended up to close behind us. Either way, not something I’d like to experience again.
![]() 10/03/2018 at 10:48 |
|
deleted
![]() 10/03/2018 at 11:01 |
|
Yeah, “I’m in control” struck me as a very optimistic way of looking at driving. As long as there are other people (or deer, or moose, or dogs, or...) nearby, your fate isn’t entirely in your own hands.
![]() 10/03/2018 at 11:03 |
|
Accepting blame is, shall we say, not one of Trump’s strengths... much like owning hypercars is not one of mine.
![]() 10/03/2018 at 11:03 |
|
That’s what happens when you brake check someone.
![]() 10/03/2018 at 11:05 |
|
It’s just that feeling of helplessness that victims of an air crash must feel right before the end. I just put my faith in the pilots, who I like to believe are in no more of a hurry to die than I am.
![]() 10/03/2018 at 11:07 |
|
Flight 370 excepted. :/
![]() 10/03/2018 at 11:07 |
|
Not far off normal actually.
If you want to triple your fear of flying subscribe to @AviationSafety on Twitter and turn notifications on
![]() 10/03/2018 at 11:09 |
|
And Germanwings 9525, and EgyptAir 990.....
![]() 10/03/2018 at 11:12 |
|
Did you see the most recent NTSB video of that?
![]() 10/03/2018 at 11:13 |
|
Incursions? On my runway?
It’s more common than you think.
![]() 10/03/2018 at 11:14 |
|
lol i’ll pass thanks :)
![]() 10/03/2018 at 11:14 |
|
I’d forgotten about those. So much tragic news, it’s easy (or just more pleasant) to forget .
![]() 10/03/2018 at 11:14 |
|
Incursions, yes. Collisions, not so much.
![]() 10/03/2018 at 11:17 |
|
![]() 10/03/2018 at 11:22 |
|
I don’t know about over there, but over here, the rules state that ultimate responsibility always falls back on the pilots.
![]() 10/03/2018 at 11:34 |
|
Yeah, it’s insane.
![]() 10/03/2018 at 12:12 |
|
brake check gone wrong
![]() 10/03/2018 at 14:27 |
|
13 feet. Oh my god.
![]() 10/03/2018 at 22:14 |
|
“Nuts. That’s a technical term.”
![]() 10/03/2018 at 22:26 |
|
They got lower than the height of a 747 tail.
![]() 10/03/2018 at 22:37 |
|
I’m curious if they tuned in the localizer or not. Using the localizer on a night visual approach is pretty basic airman ship. They must have either ignored the needle or failed to tune it in, unless it was out of service.
![]() 10/04/2018 at 08:54 |
|
The procedures for the approach to runway 28R required the first officer (as the pilot monitoring) to manually tune the instrument landing system (ILS) frequency for runway 28R, which would provide backup lateral guidance (via the localizer) during the approach to supplement the visual approach procedures. However, when the first officer set up the approach, he missed the step to manually tune the ILS frequency. The captain was required to review and verify all programming by the first officer but did not notice that the ILS frequency had not been entered.
**************
The flight crewmembers reported that they started to feel tired just after they navigated through an area of thunderstorms, which radar data indicated was about 2145 (0045 eastern daylight time [EDT]). The incident occurred about 2356, which was 0256 EDT according to the flight crew’s normal body clock time; thus, part of the incident flight occurred during a time when the flight crew would normally have been asleep (according to postincident interviews) and at a time that approximates the start of the human circadian low period described in Air Canada’s fatigue information (in this case, 0300 to 0500 EDT). In addition, at the time of the incident, the captain had been awake for more than 19 hours, and the first officer had been awake for more than 12 hours. Thus, the captain and the first officer were fatigued during the incident flight.
![]() 10/04/2018 at 08:57 |
|
I think it’s also possible that, if things lined up just right, the pilots landing would not have seen the other a/c as it would have been under the nose. It wasn’t until they were committed to the landing that they saw it, and simply couldn’t stop in time.
![]() 10/04/2018 at 09:26 |
|
It’s amazing what fatigue can do to your decision making.
![]() 10/04/2018 at 09:30 |
|
Expectation bias is a bitch.
![]() 10/04/2018 at 09:35 |
|
That too.